This repository has been archived by the owner on Jan 24, 2021. It is now read-only.
SELF HOST: Support weak and strong wildcards in URL prefixes #2978
+64
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites
Description
The Nancy.Hosting.Self library supports the rewriting of localhost URIs to wildcard URL prefixes. At the moment the rewrite feature only supports the use of the strong wildcard (http://+:etc).
There are occasions where you want to guarantee that you only pick up requests for which no other application has registered a matching prefix. In order to do this Nancy needs to rewrite the localhost URI using the weak wildcard (http://*:etc).
This pull request adds a new property to HostConfiguration called UseWeakWildcard. The property defaults to false. When it is false behaviour remains unchanged, the strong wildcard is used when deriving URL prefixes from localhost URIs. However, when it is set to true the weak wildcard gets used instead.
There are three new unit tests that show: